This is a plug-in for browsing the disassembly of PowerPC PEF-based code fragments within the Fragmalyzer.
• double-clicking on an export symbol (in a Fragmalyzer browser) will open a code browser window at that symbol.
• hyperlink-style navigation: click on symbol names in the disassembly to jump to that symbol and offset. "Go Back" command returns to the previous location.
• Markers: act like "favorites" or "bookmarks" in your web browser: save the current location so that you can jump back to it easily later.
• live-scrolling: both the symbol list and the disassembly view update instantly as you move the scrollbar thumbs.
• symbol filtering: allows you to limit the symbols shown to those with a particular prefix (e.g. all functions that start with "Debug...").
• symbol list is built from embedded traceback tables (if present), the list of exported functions, the initialization, termination, and main entrypoints, all glue code, and has "anonymous" symbols for everything else.
• you can browse code in memory, on disk, even in accelerated and native code resources!
• this browser can handle humungous code sections with no noticeable performance hit (tested quite happily with fragments as large as 17MB). For snappiest results, don't browse fragments on servers or other slow volumes.
System Requirements
• About 400K of free memory when running the Fragmalyzer, more if browsing extremely large code fragments (e.g. more than 8 megabytes of code). For best performance, scan files on faster drives (avoid servers and CD-ROMs in particular).
• This plug-in is theme-savvy (requires Mac OS 8.5 for the full effect).
Installation
Move, copy, or alias this plug-in to your Fragmalyzer “Plug-ins” folder. You can put the entire distribution folder inside the Plug-ins folder, if you like. To disable it, take it out of the Plug-ins folder, or rename the PowerPC Code Browser folder "(PowerPC Code Browser)".
Changed/fixed in 1.5
• Updated to the Fragmalyzer 1.5 plug-in API; it now requires the Fragmalyzer 1.5 or later.
• Improvements to code browser APIs for better interaction with the Section Browser plug-in (formerly Hex Wrench)
Known problems/limitations
• When the last thing in the code section is glue code, it may get classified as "data" instead.
• When there is embedded data in the code anywhere but at the end of the code section, the code browser just lumps it in with a function.
